add benchmarking #460
Merged
add benchmarking #460
+1,253
−29
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
pranaygp
force-pushed
the
pranaygp/11-28-add_benchmarking
branch
from
c84c8bc to
13b0aa9
Compare
pranaygp
force-pushed
the
pranaygp/11-28-add_benchmarking
branch
from
13b0aa9 to
441623c
Compare
pranaygp
force-pushed
the
pranaygp/11-28-add_benchmarking
branch
from
6224574 to
1af51b7
Compare
Contributor
📊 Benchmark ComparisonCross-matrix comparison of workflow performance across frameworks and backends. workflow with no steps
workflow with 1 step
workflow with 10 sequential steps
workflow with 10 parallel steps
Summary: Fastest Framework by Backend
Summary: Fastest Backend by Framework
Column Definitions
Backends:
|
pranaygp
force-pushed
the
pranaygp/11-28-add_benchmarking
branch
from
1af51b7 to
a9858e9
Compare
VaguelySerious
approved these changes
Nov 29, 2025
Member
VaguelySerious
left a comment
VaguelySerious
left a comment
There was a problem hiding this comment.
LGTM. The only thing I dislike is having a CI job that runs 15 minute (darn postgres). I wonder if there's something trivial we can do to speed that up to >=5 minutes? Just so it doesn't pollute CI too much. But feel free to merge either way and we'll speed up later.
It'd also be really cool if the bench workflows/steps could console log their ID + timestamps, so that it's trivial to check the CI logs to see where/how the runs/steps are slow. Should be a tiny change, can also do separately
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add some simple vitest based performance benchmarking for local world, postgres world, and vercel world, along with a github action to track it
Every PR will now run benchmarks across a few frameworks and all worlds. Once complete, a summary is posted with the results: https://github.com/vercel/workflow/actions/runs/19782846073/attempts/1#summary-56685707991